[PW_SID:1136046] dbus: expose per-BSS RSN capabilities - #509
Conversation
Network.Type intentionally groups all personal networks as "psk". Consumers therefore cannot distinguish PSK, SAE, and transition BSSes even though scan results retain the RSN IE. Add an optional RSN dictionary to BasicServiceSet with the advertised key management suites and pairwise and group ciphers. Use the same field and value names as wpa_supplicant's BSS.RSN property so consumers can share parsing logic. Parse bss->rsne directly so legacy WPA capabilities are not exposed as RSN.
Describe the optional RSN dictionary and its KeyMgmt, Pairwise, and Group entries.
Verify the exact D-Bus key management and cipher capabilities for WPA2-PSK, SAE, and transition BSSes.
Parse the optional RSN dictionary and include the advertised key management and cipher capabilities in the station get-bsses output.
The get-bsses table used an 18-character value column because Address was the only property. Make room for longer values such as RSN capabilities while keeping the table within 80 columns.
|
Fetch PR Prep - Setup ELL Make Distcheck Build - Configure Make Check Make Check w/Valgrind Incremental Build with patches |
|
Fetch PR GitLint Prep - Setup ELL Make Distcheck Build - Configure Make Check Make Check w/Valgrind Incremental Build with patches Autotest Runner Clang Build |
2 participants
From: Aleks Man aleksman4o@gmail.com
Network.Type intentionally groups all personal networks as "psk".
Consumers therefore cannot distinguish PSK, SAE, and transition BSSes
even though scan results retain the RSN IE.
Add an optional RSN dictionary to BasicServiceSet with the advertised
key management suites and pairwise and group ciphers. Use the same field
and value names as wpa_supplicant's BSS.RSN property so consumers can
share parsing logic.
Parse bss->rsne directly so legacy WPA capabilities are not exposed as
RSN.
src/network.c | 110 ++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 110 insertions(+)